Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f6067527ba174da35c548d8c05ec455a231c0f042fb7d18a061985efaa86c8d

Tx prefix hash: 545f824a1a1d1166cc9de7efd7d9ce1a77295a8b4bef2ab3ac823e13f93c447a
Tx public key: 14512e5de5fdc36fa8aa477697be8af8f0874804af5b3c84bb5d0f85cb74e821
Timestamp: 1583395277 Timestamp [UCT]: 2020-03-05 08:01:17 Age [y:d:h:m:s]: 05:010:15:34:40
Block: 76628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1162824 RingCT/type: yes/0
Extra: 0114512e5de5fdc36fa8aa477697be8af8f0874804af5b3c84bb5d0f85cb74e8210211000000118a2ee0d9000000000000000000

1 output(s) for total of 342.058526916000 dcy

stealth address amount amount idx
00: 05bb171424eee1027c59369ce889a922cf0d328985be69e556be0291fba3075e 342.058526916000 141061 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": 76638, "vin": [ { "gen": { "height": 76628 } } ], "vout": [ { "amount": 342058526916, "target": { "key": "05bb171424eee1027c59369ce889a922cf0d328985be69e556be0291fba3075e" } } ], "extra": [ 1, 20, 81, 46, 93, 229, 253, 195, 111, 168, 170, 71, 118, 151, 190, 138, 248, 240, 135, 72, 4, 175, 91, 60, 132, 187, 93, 15, 133, 203, 116, 232, 33, 2, 17, 0, 0, 0, 17, 138, 46, 224, 217, 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