Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfaee9f68fd1f43ed717d0134fc9e6823d0edc676ea9d5305de0c97b18cec641

Tx prefix hash: f75cff869bcd6c199eae2adefd61292c0eb130dc7d2476efe0223ca39ab152a9
Tx public key: c49a51627f33d947c3f45b9e4ee05a2e9d490677f690abc1fe487c0037aefed5
Timestamp: 1681579152 Timestamp [UCT]: 2023-04-15 17:19:12 Age [y:d:h:m:s]: 02:046:13:57:24
Block: 739260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555487 RingCT/type: yes/0
Extra: 01c49a51627f33d947c3f45b9e4ee05a2e9d490677f690abc1fe487c0037aefed5021100000001faf35c9c000000000000000000

1 output(s) for total of 2.180343691000 dcy

stealth address amount amount idx
00: d77fe61bcfe8fccfbee29886db0dde3186b55cd80be1457ea54d6af7a415163b 2.180343691000 1186099 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": 739270, "vin": [ { "gen": { "height": 739260 } } ], "vout": [ { "amount": 2180343691, "target": { "key": "d77fe61bcfe8fccfbee29886db0dde3186b55cd80be1457ea54d6af7a415163b" } } ], "extra": [ 1, 196, 154, 81, 98, 127, 51, 217, 71, 195, 244, 91, 158, 78, 224, 90, 46, 157, 73, 6, 119, 246, 144, 171, 193, 254, 72, 124, 0, 55, 174, 254, 213, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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