Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379c87f093d2667ab2c2e15d8cbf99366dca7822f338257f36e3626d3a0469d5

Tx prefix hash: 676f0e3829425e0c796e0b9b7a2dcb5a9da2c7580203ef3953db18935460f9f8
Tx public key: ef37d16649c41bbc955328a9399cae025c38a08896d63386b126ffb07085b897
Timestamp: 1580009655 Timestamp [UCT]: 2020-01-26 03:34:15 Age [y:d:h:m:s]: 04:336:17:51:21
Block: 52973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130873 RingCT/type: yes/0
Extra: 01ef37d16649c41bbc955328a9399cae025c38a08896d63386b126ffb07085b897021100000002391a8d0e000000000000000000

1 output(s) for total of 409.712571091000 dcy

stealth address amount amount idx
00: 708c42040a92f72f1e00b5815bc10e01adfd57b61adad7fea62bd52dfdaef4e1 409.712571091000 98250 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": 52983, "vin": [ { "gen": { "height": 52973 } } ], "vout": [ { "amount": 409712571091, "target": { "key": "708c42040a92f72f1e00b5815bc10e01adfd57b61adad7fea62bd52dfdaef4e1" } } ], "extra": [ 1, 239, 55, 209, 102, 73, 196, 27, 188, 149, 83, 40, 169, 57, 156, 174, 2, 92, 56, 160, 136, 150, 214, 51, 134, 177, 38, 255, 176, 112, 133, 184, 151, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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