Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9ae0332ff69dc2c0f07cb75b45c54c2411a2bafd359fa34ed7ae8c9ac02c05

Tx prefix hash: 565a0b4851df2efd9d97280602fce80059d1320c998caef63679ee52c6719bce
Tx public key: 634db7cd3668ecf9d53122b0f14bfa798e7f8a1f3cac5924c1ea5f1c48136266
Timestamp: 1581220036 Timestamp [UCT]: 2020-02-09 03:47:16 Age [y:d:h:m:s]: 05:001:17:14:53
Block: 61020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154023 RingCT/type: yes/0
Extra: 01634db7cd3668ecf9d53122b0f14bfa798e7f8a1f3cac5924c1ea5f1c481362660211000000174943cd9f000000000000000000

1 output(s) for total of 385.315275177000 dcy

stealth address amount amount idx
00: 8657dfc57a8b33895590024d7d97fd5d7f8c029b664427db414e6824ea4b2a97 385.315275177000 112477 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": 61030, "vin": [ { "gen": { "height": 61020 } } ], "vout": [ { "amount": 385315275177, "target": { "key": "8657dfc57a8b33895590024d7d97fd5d7f8c029b664427db414e6824ea4b2a97" } } ], "extra": [ 1, 99, 77, 183, 205, 54, 104, 236, 249, 213, 49, 34, 176, 241, 75, 250, 121, 142, 127, 138, 31, 60, 172, 89, 36, 193, 234, 95, 28, 72, 19, 98, 102, 2, 17, 0, 0, 0, 23, 73, 67, 205, 159, 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