Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba90afcdd18a26fe411e5327377ffbe0b94b9907cea9a26bce06ddcd84b22a77

Tx prefix hash: 58b0aef291e41dc28d2701a6972a16e304231091d0d69f3d4dfef2a25b33af69
Tx public key: 2bd53d528c358c0df9a0cc099e96d39d87989d218239f354c2636fff1045a002
Timestamp: 1701164780 Timestamp [UCT]: 2023-11-28 09:46:20 Age [y:d:h:m:s]: 01:140:10:39:57
Block: 901398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361547 RingCT/type: yes/0
Extra: 012bd53d528c358c0df9a0cc099e96d39d87989d218239f354c2636fff1045a0020211000000024b8f5122000000000000000000

1 output(s) for total of 0.632840433000 dcy

stealth address amount amount idx
00: 81a429456d7817fe31e08b4d30c2337186e29b6e514282f8705e12efab3f11c7 0.632840433000 1357957 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": 901408, "vin": [ { "gen": { "height": 901398 } } ], "vout": [ { "amount": 632840433, "target": { "key": "81a429456d7817fe31e08b4d30c2337186e29b6e514282f8705e12efab3f11c7" } } ], "extra": [ 1, 43, 213, 61, 82, 140, 53, 140, 13, 249, 160, 204, 9, 158, 150, 211, 157, 135, 152, 157, 33, 130, 57, 243, 84, 194, 99, 111, 255, 16, 69, 160, 2, 2, 17, 0, 0, 0, 2, 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