Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd621e1cac02ef7ce0fb4ee912679b43c2d4f60b5340f378c7045155a1de33e1

Tx prefix hash: daf9f2117b2f046f38f5231d4f964fb120b8b94763dc2bee2ee7ffc4420b086c
Tx public key: 29464f4afc32e85ebdb42322c5b5f92c37d9ebebb0960050574e2822db95dd3b
Timestamp: 1698380566 Timestamp [UCT]: 2023-10-27 04:22:46 Age [y:d:h:m:s]: 01:154:09:30:44
Block: 878539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371333 RingCT/type: yes/0
Extra: 0129464f4afc32e85ebdb42322c5b5f92c37d9ebebb0960050574e2822db95dd3b0211000000034b8f5122000000000000000000

1 output(s) for total of 0.753417336000 dcy

stealth address amount amount idx
00: 8cb67f9ef8a109368c9a45dd9836427b22a44e2fea3e30d777b75b2fb71f18ea 0.753417336000 1333989 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": 878549, "vin": [ { "gen": { "height": 878539 } } ], "vout": [ { "amount": 753417336, "target": { "key": "8cb67f9ef8a109368c9a45dd9836427b22a44e2fea3e30d777b75b2fb71f18ea" } } ], "extra": [ 1, 41, 70, 79, 74, 252, 50, 232, 94, 189, 180, 35, 34, 197, 181, 249, 44, 55, 217, 235, 235, 176, 150, 0, 80, 87, 78, 40, 34, 219, 149, 221, 59, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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