Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973fd801342de41e2084f5baea0b2058ab29458353b85f8bb3aa480650d4f662

Tx prefix hash: 8d9e39075dfd0899887936c158f07595338992e2e0f378368be8600e902230a5
Tx public key: e1c6ab9c71ecab1fd60c390235c16a063852e41c06d0c9188c634386d85a541f
Timestamp: 1702099131 Timestamp [UCT]: 2023-12-09 05:18:51 Age [y:d:h:m:s]: 01:362:21:52:19
Block: 909141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518269 RingCT/type: yes/0
Extra: 01e1c6ab9c71ecab1fd60c390235c16a063852e41c06d0c9188c634386d85a541f021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a36f382711ad9bc937058abe16d8aa63758a46f2f05a1f2c056eaa482a6c08 0.600000000000 1366208 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": 909151, "vin": [ { "gen": { "height": 909141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a36f382711ad9bc937058abe16d8aa63758a46f2f05a1f2c056eaa482a6c08" } } ], "extra": [ 1, 225, 198, 171, 156, 113, 236, 171, 31, 214, 12, 57, 2, 53, 193, 106, 6, 56, 82, 228, 28, 6, 208, 201, 24, 140, 99, 67, 134, 216, 90, 84, 31, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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