Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb3020489e866449420b807c49acb2412a3cbf84aa388dd62307e75590aba5ed

Tx prefix hash: b76fdcc10104cb43f7b0c8067a5d9f310cfea89ecbb9d6594b6b012a7e73a09f
Tx public key: 65415d01f4a7e5905007f118f52f6ba4cff0dcb4c5d24a82300b581963890f4b
Timestamp: 1580512637 Timestamp [UCT]: 2020-01-31 23:17:17 Age [y:d:h:m:s]: 04:294:03:42:08
Block: 56318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101216 RingCT/type: yes/0
Extra: 0165415d01f4a7e5905007f118f52f6ba4cff0dcb4c5d24a82300b581963890f4b0211000000044ac5aa02000000000000000000

1 output(s) for total of 399.388826817000 dcy

stealth address amount amount idx
00: 9e5475950efb01ea47901850095e55b1b79f7507b1137f2e3d816bd3b6b07cb7 399.388826817000 103832 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": 56328, "vin": [ { "gen": { "height": 56318 } } ], "vout": [ { "amount": 399388826817, "target": { "key": "9e5475950efb01ea47901850095e55b1b79f7507b1137f2e3d816bd3b6b07cb7" } } ], "extra": [ 1, 101, 65, 93, 1, 244, 167, 229, 144, 80, 7, 241, 24, 245, 47, 107, 164, 207, 240, 220, 180, 197, 210, 74, 130, 48, 11, 88, 25, 99, 137, 15, 75, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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