Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5076ae277b749a3f5619baa499c18716fbb769b0304baee04114047af4433778

Tx prefix hash: 85927cfe3f5d99c9d7b5b9a030b1328b27673933f88be2b2e22a9b0250bdbc45
Tx public key: 1dc9b18be758dc84528e906931b20f381fb2d467709490212c2d8e2293631a7d
Timestamp: 1705329720 Timestamp [UCT]: 2024-01-15 14:42:00 Age [y:d:h:m:s]: 00:358:02:26:34
Block: 935917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256385 RingCT/type: yes/0
Extra: 011dc9b18be758dc84528e906931b20f381fb2d467709490212c2d8e2293631a7d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1e28428429e586547bca79d4bb7e629d6db68b7c9a82bef77ba431553eb73f9 0.600000000000 1393935 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": 935927, "vin": [ { "gen": { "height": 935917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1e28428429e586547bca79d4bb7e629d6db68b7c9a82bef77ba431553eb73f9" } } ], "extra": [ 1, 29, 201, 177, 139, 231, 88, 220, 132, 82, 142, 144, 105, 49, 178, 15, 56, 31, 178, 212, 103, 112, 148, 144, 33, 44, 45, 142, 34, 147, 99, 26, 125, 2, 17, 0, 0, 0, 1, 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