Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17027098edaac2cb2cb44d223096d5b5392b7433c937701d241afd7336809ce

Tx prefix hash: 5b21ba9ac7aab6689f9b52584db2f07e1e9e6da7872da5dc0bdf3b6ac95ea9bd
Tx public key: 461e1775bf9251fd0060fdaa708fe0ed10a0aefabfc568feb68c1c22c4c6b443
Timestamp: 1711557788 Timestamp [UCT]: 2024-03-27 16:43:08 Age [y:d:h:m:s]: 01:085:15:10:40
Block: 987591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322020 RingCT/type: yes/0
Extra: 01461e1775bf9251fd0060fdaa708fe0ed10a0aefabfc568feb68c1c22c4c6b44302110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 875139e1fc2d4e9f9108489024618f6a799cfe3c4afeb99877f8a82e5e70fda4 0.600000000000 1447844 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": 987601, "vin": [ { "gen": { "height": 987591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875139e1fc2d4e9f9108489024618f6a799cfe3c4afeb99877f8a82e5e70fda4" } } ], "extra": [ 1, 70, 30, 23, 117, 191, 146, 81, 253, 0, 96, 253, 170, 112, 143, 224, 237, 16, 160, 174, 250, 191, 197, 104, 254, 182, 140, 28, 34, 196, 198, 180, 67, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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