Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b27cebcb59f15fceebda2b13e46b3b15a6c5222048992c2db2ad03b5bf4f340c

Tx prefix hash: b06d1fe4c5d176353c9db0b179befa09cb9d00abb379a9249301702ad08fb54e
Tx public key: fa3109ed7ae15b02995cf01900be3f5d072f94d68bd67c3d9da07465492ea44c
Timestamp: 1672504956 Timestamp [UCT]: 2022-12-31 16:42:36 Age [y:d:h:m:s]: 02:282:06:33:59
Block: 664660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721102 RingCT/type: yes/0
Extra: 01fa3109ed7ae15b02995cf01900be3f5d072f94d68bd67c3d9da07465492ea44c02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.852170238000 dcy

stealth address amount amount idx
00: 309bdffa1f8bafab6c1f4069e83221898ec5b74d735055e8d706c6c195d530e9 3.852170238000 1105663 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": 664670, "vin": [ { "gen": { "height": 664660 } } ], "vout": [ { "amount": 3852170238, "target": { "key": "309bdffa1f8bafab6c1f4069e83221898ec5b74d735055e8d706c6c195d530e9" } } ], "extra": [ 1, 250, 49, 9, 237, 122, 225, 91, 2, 153, 92, 240, 25, 0, 190, 63, 93, 7, 47, 148, 214, 139, 214, 124, 61, 157, 160, 116, 101, 73, 46, 164, 76, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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