Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31cc354ac7df1b07a8716cc3f2bf627d0afe5c1a09b5ff5b3cf33b3397f3040

Tx prefix hash: 1b1330dca5c671939b19f8a375b7dc1e4df3f9b44655ff0e12e8b1acfc2b928c
Tx public key: a74960600836ce231788e5cfcfc4ed9dbbbbbfd26784320ac486493ba2aea877
Timestamp: 1702742213 Timestamp [UCT]: 2023-12-16 15:56:53 Age [y:d:h:m:s]: 01:329:20:32:40
Block: 914479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494601 RingCT/type: yes/0
Extra: 01a74960600836ce231788e5cfcfc4ed9dbbbbbfd26784320ac486493ba2aea877021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d7a446bfb3721b7161ae6d6f8a4731a40e32ad712d0e88758874ed16713963c 0.600000000000 1371795 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": 914489, "vin": [ { "gen": { "height": 914479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d7a446bfb3721b7161ae6d6f8a4731a40e32ad712d0e88758874ed16713963c" } } ], "extra": [ 1, 167, 73, 96, 96, 8, 54, 206, 35, 23, 136, 229, 207, 207, 196, 237, 157, 187, 187, 191, 210, 103, 132, 50, 10, 196, 134, 73, 59, 162, 174, 168, 119, 2, 17, 0, 0, 0, 3, 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