Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b20f315114d753e4ebea764e6b7c0e5312f006239eb4385ec2e366a469a89aea

Tx prefix hash: daca7d0e0c93603667a3ed1fc8f03d59097f5258a5fb695b873d0b641278a0d0
Tx public key: 64c1217d0e0aa0bd12ad3218bd27c6bb8013844e1e62335859cc8aa74e50b427
Timestamp: 1639221750 Timestamp [UCT]: 2021-12-11 11:22:30 Age [y:d:h:m:s]: 03:093:11:29:36
Block: 393143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 845573 RingCT/type: yes/0
Extra: 0164c1217d0e0aa0bd12ad3218bd27c6bb8013844e1e62335859cc8aa74e50b42702110000000676899486000000000000000000

1 output(s) for total of 30.574150641000 dcy

stealth address amount amount idx
00: 6f999f994c910108aaf030d85c406221349f8d1ed79c01b0903fe26bdebf8937 30.574150641000 790298 of 0

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": 393153, "vin": [ { "gen": { "height": 393143 } } ], "vout": [ { "amount": 30574150641, "target": { "key": "6f999f994c910108aaf030d85c406221349f8d1ed79c01b0903fe26bdebf8937" } } ], "extra": [ 1, 100, 193, 33, 125, 14, 10, 160, 189, 18, 173, 50, 24, 189, 39, 198, 187, 128, 19, 132, 78, 30, 98, 51, 88, 89, 204, 138, 167, 78, 80, 180, 39, 2, 17, 0, 0, 0, 6, 118, 137, 148, 134, 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