Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9163f5c2f997d33beb08a37df63bff53660a8a3f2fc519c7e3120c2eea0dea49

Tx prefix hash: d2593c0f92bbea4bf7db955e474f1b95fbb66ddb25d02a0b072e5d415d7a55f1
Tx public key: a405f8a8dff96cbdeb5ab6e03d52fad833a3e35f98062d78cf2636c2a0a8e472
Timestamp: 1734823041 Timestamp [UCT]: 2024-12-21 23:17:21 Age [y:d:h:m:s]: 00:178:07:29:44
Block: 1180367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127115 RingCT/type: yes/0
Extra: 01a405f8a8dff96cbdeb5ab6e03d52fad833a3e35f98062d78cf2636c2a0a8e47202110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fe2f634537cb640a8e0731fe3ff146232e6d61b3733d0ab42d0540d14e6bff2 0.600000000000 1666778 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": 1180377, "vin": [ { "gen": { "height": 1180367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fe2f634537cb640a8e0731fe3ff146232e6d61b3733d0ab42d0540d14e6bff2" } } ], "extra": [ 1, 164, 5, 248, 168, 223, 249, 108, 189, 235, 90, 182, 224, 61, 82, 250, 216, 51, 163, 227, 95, 152, 6, 45, 120, 207, 38, 54, 194, 160, 168, 228, 114, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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