Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32eacd9882c25a392c11ffd1beee654a0cb11e10052a5043c020ad0a77fb1929

Tx prefix hash: 3dfe99818ba7263fcf0a6e40f90ef6a6c9f24536de52b41dac2cbcf8cc50d484
Tx public key: 74c28e3381e70ccae34965e92547359fa484a7f13c38f5d871a0346c0aea4ec5
Timestamp: 1711865577 Timestamp [UCT]: 2024-03-31 06:12:57 Age [y:d:h:m:s]: 01:002:00:03:24
Block: 990137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262358 RingCT/type: yes/0
Extra: 0174c28e3381e70ccae34965e92547359fa484a7f13c38f5d871a0346c0aea4ec502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83d4a9e2e656e02840284ed0dd9d983e89ebb579d920e4b2ef0b7ced2d9dc6ba 0.600000000000 1450459 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": 990147, "vin": [ { "gen": { "height": 990137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83d4a9e2e656e02840284ed0dd9d983e89ebb579d920e4b2ef0b7ced2d9dc6ba" } } ], "extra": [ 1, 116, 194, 142, 51, 129, 231, 12, 202, 227, 73, 101, 233, 37, 71, 53, 159, 164, 132, 167, 241, 60, 56, 245, 216, 113, 160, 52, 108, 10, 234, 78, 197, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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