Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2c3c2b47b264bf3182190b7dc1a59e4f002c786de7bd4e69e088bdaf58b7ce

Tx prefix hash: 3896534c9f1ff47b908fffff3f8289a0faafc15f228c1a0063a004d7337a8194
Tx public key: 9772ed87127eae9b5a91d36797103cb657f2c64cf4520a2ae57b92365b54a40b
Timestamp: 1703195042 Timestamp [UCT]: 2023-12-21 21:44:02 Age [y:d:h:m:s]: 01:108:20:45:57
Block: 918228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338930 RingCT/type: yes/0
Extra: 019772ed87127eae9b5a91d36797103cb657f2c64cf4520a2ae57b92365b54a40b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c00e2d4741f78ee5ae260519a02ce35682ff3cc0e6f4f60959fd0e3c708fafa5 0.600000000000 1375870 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": 918238, "vin": [ { "gen": { "height": 918228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c00e2d4741f78ee5ae260519a02ce35682ff3cc0e6f4f60959fd0e3c708fafa5" } } ], "extra": [ 1, 151, 114, 237, 135, 18, 126, 174, 155, 90, 145, 211, 103, 151, 16, 60, 182, 87, 242, 198, 76, 244, 82, 10, 42, 229, 123, 146, 54, 91, 84, 164, 11, 2, 17, 0, 0, 0, 2, 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