Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 953d53ceca8338f371373d98da114876b4d9f43eeb3917412495b005aab7ce57

Tx prefix hash: 9cb3d6fc10da9916135eae43b74884aa726898c4bad4ddc05321a19542a91dc5
Tx public key: 9d474d8cffbe4ea8cf1f8a25e01c5c2adbba303f6f3471583e7d4de68e6003c0
Timestamp: 1705289377 Timestamp [UCT]: 2024-01-15 03:29:37 Age [y:d:h:m:s]: 01:122:23:26:55
Block: 935570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349033 RingCT/type: yes/0
Extra: 019d474d8cffbe4ea8cf1f8a25e01c5c2adbba303f6f3471583e7d4de68e6003c002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 042d21c17ef6f211f089ef9664570bb03724d9839a6a70f7919ea4cbaad68075 0.600000000000 1393586 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": 935580, "vin": [ { "gen": { "height": 935570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "042d21c17ef6f211f089ef9664570bb03724d9839a6a70f7919ea4cbaad68075" } } ], "extra": [ 1, 157, 71, 77, 140, 255, 190, 78, 168, 207, 31, 138, 37, 224, 28, 92, 42, 219, 186, 48, 63, 111, 52, 113, 88, 62, 125, 77, 230, 142, 96, 3, 192, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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