Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7c3e5676236ef7c813c8ec283598beb517506b5ae3238d4888f9c304a2fb0c

Tx prefix hash: 0fb99076819b226d7a40a8a0a5651cb3a6e7049474554b6bb272e70432262c93
Tx public key: 375d6893d8f5e9218e55ec3b5cd1fa7e7c1436ace8ba5583cf665ae6e99947d1
Timestamp: 1626479233 Timestamp [UCT]: 2021-07-16 23:47:13 Age [y:d:h:m:s]: 03:231:12:22:29
Block: 295449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 936495 RingCT/type: yes/0
Extra: 01375d6893d8f5e9218e55ec3b5cd1fa7e7c1436ace8ba5583cf665ae6e99947d10211000000049cd60737000000000000000000

1 output(s) for total of 64.427371466000 dcy

stealth address amount amount idx
00: 797cd554725d1c34a387c5e2ade86200a8a48863c0c72fcb6430546c28199784 64.427371466000 618701 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": 295459, "vin": [ { "gen": { "height": 295449 } } ], "vout": [ { "amount": 64427371466, "target": { "key": "797cd554725d1c34a387c5e2ade86200a8a48863c0c72fcb6430546c28199784" } } ], "extra": [ 1, 55, 93, 104, 147, 216, 245, 233, 33, 142, 85, 236, 59, 92, 209, 250, 126, 124, 20, 54, 172, 232, 186, 85, 131, 207, 102, 90, 230, 233, 153, 71, 209, 2, 17, 0, 0, 0, 4, 156, 214, 7, 55, 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