Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f83d09fb28c6b661612adcad9302109a219ae5c2ec2135f3bb500f3d9e183afa

Tx prefix hash: d7e6b1c9b55191a5fe33f543d7029faf13f667a755933f2520a587ec6763d4ba
Tx public key: 18e37fef03eb2da3bceaa190701e71c814dfd11c5cb6838faa4bd4c3159d9ff3
Timestamp: 1706518908 Timestamp [UCT]: 2024-01-29 09:01:48 Age [y:d:h:m:s]: 01:133:19:58:13
Block: 945771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356762 RingCT/type: yes/0
Extra: 0118e37fef03eb2da3bceaa190701e71c814dfd11c5cb6838faa4bd4c3159d9ff30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0a61e733a58c1d496393652585ad439a2de44aeebca2a74f9170f1ed2350a4 0.600000000000 1404089 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 945781, "vin": [ { "gen": { "height": 945771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0a61e733a58c1d496393652585ad439a2de44aeebca2a74f9170f1ed2350a4" } } ], "extra": [ 1, 24, 227, 127, 239, 3, 235, 45, 163, 188, 234, 161, 144, 112, 30, 113, 200, 20, 223, 209, 28, 92, 182, 131, 143, 170, 75, 212, 195, 21, 157, 159, 243, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8