Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bab4eddad3cc96f15c933b59cb4a0e8faa91360e445bb68d311d5309f8e805

Tx prefix hash: 31d11c9dbc0f075ce2002a73711cff0b62d28ca33bafe453f1fe421a33049ab6
Tx public key: ac9a69afbdd1407d3a27c5c48f6e121851f3a13cb6d60d69a15fb5b885e91334
Timestamp: 1729582142 Timestamp [UCT]: 2024-10-22 07:29:02 Age [y:d:h:m:s]: 01:012:18:42:33
Block: 1136959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267515 RingCT/type: yes/0
Extra: 01ac9a69afbdd1407d3a27c5c48f6e121851f3a13cb6d60d69a15fb5b885e91334021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa509039a3b6220dd96f5836ff649d0920fdd25c6696a7287771bc63384e9a08 0.600000000000 1620362 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": 1136969, "vin": [ { "gen": { "height": 1136959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa509039a3b6220dd96f5836ff649d0920fdd25c6696a7287771bc63384e9a08" } } ], "extra": [ 1, 172, 154, 105, 175, 189, 209, 64, 125, 58, 39, 197, 196, 143, 110, 18, 24, 81, 243, 161, 60, 182, 214, 13, 105, 161, 95, 181, 184, 133, 233, 19, 52, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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