Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737ca73dcb93bcd45f70a6a7119a28db1825f3bcd9d06a4ef26c4ca85e939428

Tx prefix hash: 2e19fe81ff498a500d44371b96c8d805c481d7b3323e7bb9ca9aa5c70c843bf7
Tx public key: 8d44aff4cf0e368126743c8da0eafd64a89c3ab55e8cfe54b6288d00f275b680
Timestamp: 1766067121 Timestamp [UCT]: 2025-12-18 14:12:01 Age [y:d:h:m:s]: 00:003:01:36:35
Block: 1436336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2205 RingCT/type: yes/0
Extra: 018d44aff4cf0e368126743c8da0eafd64a89c3ab55e8cfe54b6288d00f275b680021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af3a4bb3bb9f075ac98e74bc7f4c27ad25a15993a27fea4b007027cffed7a4b4 0.600000000000 1925141 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": 1436346, "vin": [ { "gen": { "height": 1436336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af3a4bb3bb9f075ac98e74bc7f4c27ad25a15993a27fea4b007027cffed7a4b4" } } ], "extra": [ 1, 141, 68, 175, 244, 207, 14, 54, 129, 38, 116, 60, 141, 160, 234, 253, 100, 168, 156, 58, 181, 94, 140, 254, 84, 182, 40, 141, 0, 242, 117, 182, 128, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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