Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6981e85b5deb5c6d2353095eba5bdab8978a2a32898a32f07d9e8305143433

Tx prefix hash: 6d12037edcb179a27c95679519b3fd81c60da16332c4d2f421952cf7dabc4479
Tx public key: 9a1e1f045142421b995ebe190dbb25e59c86d6446cf8213d6fd8d05f00a4f97b
Timestamp: 1706582256 Timestamp [UCT]: 2024-01-30 02:37:36 Age [y:d:h:m:s]: 01:289:21:28:06
Block: 946289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466000 RingCT/type: yes/0
Extra: 019a1e1f045142421b995ebe190dbb25e59c86d6446cf8213d6fd8d05f00a4f97b0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d7c46c4a0d99c6aa793ece897aa7852e9b93aff08c078b08ef648df964e7d35 0.600000000000 1404621 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": 946299, "vin": [ { "gen": { "height": 946289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d7c46c4a0d99c6aa793ece897aa7852e9b93aff08c078b08ef648df964e7d35" } } ], "extra": [ 1, 154, 30, 31, 4, 81, 66, 66, 27, 153, 94, 190, 25, 13, 187, 37, 229, 156, 134, 214, 68, 108, 248, 33, 61, 111, 216, 208, 95, 0, 164, 249, 123, 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