Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ca924553795187dc818a34889f32dd7e01e191deb62d741d36c7aa29ae69c87

Tx prefix hash: 352a97f9583ee1c05f7fa9f6e03cf2aa722ae245d4ae13e04e358802dc70e781
Tx public key: 17f4b113938639ec81e58df5b462af1156aa0ef2d8ad9e2fbcf2703aa0bc1e06
Timestamp: 1723023264 Timestamp [UCT]: 2024-08-07 09:34:24 Age [y:d:h:m:s]: 00:253:23:27:33
Block: 1082617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181418 RingCT/type: yes/0
Extra: 0117f4b113938639ec81e58df5b462af1156aa0ef2d8ad9e2fbcf2703aa0bc1e0602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78580248e9c9978f573a0b4432ce4d5b361d271f822c0dd89e9a116b1fc7bfc5 0.600000000000 1556446 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": 1082627, "vin": [ { "gen": { "height": 1082617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78580248e9c9978f573a0b4432ce4d5b361d271f822c0dd89e9a116b1fc7bfc5" } } ], "extra": [ 1, 23, 244, 177, 19, 147, 134, 57, 236, 129, 229, 141, 245, 180, 98, 175, 17, 86, 170, 14, 242, 216, 173, 158, 47, 188, 242, 112, 58, 160, 188, 30, 6, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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