Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f06ce58c6998cfa93c7bd12f10307a1a3aed55ee48b4f8d21792b5314ded899f

Tx prefix hash: 5408422ef56c76135f2f87425961f6b99d619d512328fffe4de9b8e16b5bd366
Tx public key: 06a11bafaba8d8fc8cd75ba7e5fc87499c0fa0c4e185877eb531c41d862ff81e
Timestamp: 1582131680 Timestamp [UCT]: 2020-02-19 17:01:20 Age [y:d:h:m:s]: 04:260:19:31:26
Block: 68412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078667 RingCT/type: yes/0
Extra: 0106a11bafaba8d8fc8cd75ba7e5fc87499c0fa0c4e185877eb531c41d862ff81e0211000000010aca7173000000000000000000

1 output(s) for total of 364.194461200000 dcy

stealth address amount amount idx
00: 8fc13532a14abd4e323ef4935bb79f45cef72e2797d6a7789cb3843adb1e96f0 364.194461200000 126006 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": 68422, "vin": [ { "gen": { "height": 68412 } } ], "vout": [ { "amount": 364194461200, "target": { "key": "8fc13532a14abd4e323ef4935bb79f45cef72e2797d6a7789cb3843adb1e96f0" } } ], "extra": [ 1, 6, 161, 27, 175, 171, 168, 216, 252, 140, 215, 91, 167, 229, 252, 135, 73, 156, 15, 160, 196, 225, 133, 135, 126, 181, 49, 196, 29, 134, 47, 248, 30, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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