Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 545fcdc23e5e6f4109de21a1ef47f784d1555c3a877da3fd18155e16173e61a8

Tx prefix hash: 606d6195454cd9ca168b0428f857faf80d6ca4b18f9b13bb3af3e244b61b3132
Tx public key: d4bd9db8253ef27dc31cf8657527022997d3db7ee9b24a3cf323c4b2a6a34170
Timestamp: 1727498171 Timestamp [UCT]: 2024-09-28 04:36:11 Age [y:d:h:m:s]: 01:042:09:22:14
Block: 1119723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288690 RingCT/type: yes/0
Extra: 01d4bd9db8253ef27dc31cf8657527022997d3db7ee9b24a3cf323c4b2a6a3417002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afb9e06ba38d3fb25fc9ec524f618bb3e7a877df771d94d0ab4a185e529ad593 0.600000000000 1601384 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": 1119733, "vin": [ { "gen": { "height": 1119723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afb9e06ba38d3fb25fc9ec524f618bb3e7a877df771d94d0ab4a185e529ad593" } } ], "extra": [ 1, 212, 189, 157, 184, 37, 62, 242, 125, 195, 28, 248, 101, 117, 39, 2, 41, 151, 211, 219, 126, 233, 178, 74, 60, 243, 35, 196, 178, 166, 163, 65, 112, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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