Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76483bb4e1fefb9fb6b4cf2d7823c8ece815f7871a45dbc9e16964b5074a69ad

Tx prefix hash: 2734942f8eba937ab05178a9cd40e23f709483fa6dddcf661d3f09b9251aebc4
Tx public key: 0f4ac164492b5743f0f13a336867ac015dba2f9b2e4718ede034bddc0e261713
Timestamp: 1578259534 Timestamp [UCT]: 2020-01-05 21:25:34 Age [y:d:h:m:s]: 05:100:20:03:49
Block: 39473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221955 RingCT/type: yes/0
Extra: 010f4ac164492b5743f0f13a336867ac015dba2f9b2e4718ede034bddc0e26171302110000000bd81c26c0000000000000000000

1 output(s) for total of 454.171452254000 dcy

stealth address amount amount idx
00: 707ebb6cea4823af52cdad3a9fb1a1a3030641e42c2d23124656c9b719d15f94 454.171452254000 68152 of 0

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": 39483, "vin": [ { "gen": { "height": 39473 } } ], "vout": [ { "amount": 454171452254, "target": { "key": "707ebb6cea4823af52cdad3a9fb1a1a3030641e42c2d23124656c9b719d15f94" } } ], "extra": [ 1, 15, 74, 193, 100, 73, 43, 87, 67, 240, 241, 58, 51, 104, 103, 172, 1, 93, 186, 47, 155, 46, 71, 24, 237, 224, 52, 189, 220, 14, 38, 23, 19, 2, 17, 0, 0, 0, 11, 216, 28, 38, 192, 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