Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 138af5b97d6254315ced7b8d2e2cf9d6069920f769b36d9db2607dda90b5f3bb

Tx prefix hash: 4169fb976a1206a83daa2863f58d75fb64a01c26d81a3ac89bbbf11662e63efc
Tx public key: 999aa778caeadc2160e3ca17a367eac06c3ef0b83c5d7dc0fe49c3efd3771bf3
Timestamp: 1713384102 Timestamp [UCT]: 2024-04-17 20:01:42 Age [y:d:h:m:s]: 01:250:00:37:11
Block: 1002703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437402 RingCT/type: yes/0
Extra: 01999aa778caeadc2160e3ca17a367eac06c3ef0b83c5d7dc0fe49c3efd3771bf302110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86ec785ccf2b7ee71244916d9ee294fab46050ae8e3bf1829ecfbad914abdcd6 0.600000000000 1463223 of 15

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": 1002713, "vin": [ { "gen": { "height": 1002703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86ec785ccf2b7ee71244916d9ee294fab46050ae8e3bf1829ecfbad914abdcd6" } } ], "extra": [ 1, 153, 154, 167, 120, 202, 234, 220, 33, 96, 227, 202, 23, 163, 103, 234, 192, 108, 62, 240, 184, 60, 93, 125, 192, 254, 73, 195, 239, 211, 119, 27, 243, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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