Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 796dbb9083ee76836b97848a199d21152625cc4988f15f466129bd1456f924b8

Tx prefix hash: bd99951d4fb1485d7fe6c225cac7efba81db2db0b632b89610d8c22731208d6f
Tx public key: 3ef83086342ab204fc2f831a4b47ea00d433616c55a63807d06cb5f461a3b46d
Timestamp: 1577044257 Timestamp [UCT]: 2019-12-22 19:50:57 Age [y:d:h:m:s]: 04:343:16:37:33
Block: 29727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134542 RingCT/type: yes/0
Extra: 013ef83086342ab204fc2f831a4b47ea00d433616c55a63807d06cb5f461a3b46d0211000000094943cd9f000000000000000000

1 output(s) for total of 489.218612331000 dcy

stealth address amount amount idx
00: 1c7fc2460b1c017c41d7f19e2491d5a053f4368bd851c97348376f1e5bae92ec 489.218612331000 48953 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": 29737, "vin": [ { "gen": { "height": 29727 } } ], "vout": [ { "amount": 489218612331, "target": { "key": "1c7fc2460b1c017c41d7f19e2491d5a053f4368bd851c97348376f1e5bae92ec" } } ], "extra": [ 1, 62, 248, 48, 134, 52, 42, 178, 4, 252, 47, 131, 26, 75, 71, 234, 0, 212, 51, 97, 108, 85, 166, 56, 7, 208, 108, 181, 244, 97, 163, 180, 109, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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