Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efabe31b7444adc7fd46d4c6f8b8d64a98fe2c9c047f83b5d1f4ef2a806fd7ce

Tx prefix hash: 44a1f20690100e31a72b94a9e18af439522f4930d4a1ab0e9f5067d8b077a58a
Tx public key: 0cb6cdaac93b98ac4069be8be79acf9c13417fb278179b6203dcbb48fac63fb4
Timestamp: 1714204169 Timestamp [UCT]: 2024-04-27 07:49:29 Age [y:d:h:m:s]: 00:306:06:05:28
Block: 1009499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218911 RingCT/type: yes/0
Extra: 010cb6cdaac93b98ac4069be8be79acf9c13417fb278179b6203dcbb48fac63fb40211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11943dfd8e2a0fa3bd4d7b5e1892cb1abbf2e3bf1f8374223c109a7a9344eaa6 0.600000000000 1471185 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": 1009509, "vin": [ { "gen": { "height": 1009499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11943dfd8e2a0fa3bd4d7b5e1892cb1abbf2e3bf1f8374223c109a7a9344eaa6" } } ], "extra": [ 1, 12, 182, 205, 170, 201, 59, 152, 172, 64, 105, 190, 139, 231, 154, 207, 156, 19, 65, 127, 178, 120, 23, 155, 98, 3, 220, 187, 72, 250, 198, 63, 180, 2, 17, 0, 0, 0, 5, 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