Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384f598627a16733495bab07adfec1ffd9cb0c000e1dcd4492eaf2923a792a99

Tx prefix hash: fbcb125bef60d3e50ecd5a75df49a6e8c9ce6d45b1663a5666879a89551d722a
Tx public key: 16a1dd31e5ae728d1ec8689f1eb280e40c08598fcf263e1bfe0ea897a6a660a2
Timestamp: 1715210754 Timestamp [UCT]: 2024-05-08 23:25:54 Age [y:d:h:m:s]: 01:186:01:48:59
Block: 1017858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391597 RingCT/type: yes/0
Extra: 0116a1dd31e5ae728d1ec8689f1eb280e40c08598fcf263e1bfe0ea897a6a660a20211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c28be5323f7e33c4bd86b175145a0a266f2ce0c0bf2dd78eba88f9d3e9c6bf09 0.600000000000 1481643 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": 1017868, "vin": [ { "gen": { "height": 1017858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c28be5323f7e33c4bd86b175145a0a266f2ce0c0bf2dd78eba88f9d3e9c6bf09" } } ], "extra": [ 1, 22, 161, 221, 49, 229, 174, 114, 141, 30, 200, 104, 159, 30, 178, 128, 228, 12, 8, 89, 143, 207, 38, 62, 27, 254, 14, 168, 151, 166, 166, 96, 162, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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