Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a7c024d36f271b6216ea92753bdce16dbc4b272aaecad5df21d6d2e2f414611

Tx prefix hash: 093ba931284a1582728585b928efffa60d4ff7c361f7bb298c6ba400d1f2a32d
Tx public key: d0c1fe4aac0fb194624f08e0cf804f7651ea41311eb15d2fcf58b7588fdd04bc
Timestamp: 1673087860 Timestamp [UCT]: 2023-01-07 10:37:40 Age [y:d:h:m:s]: 02:302:00:29:30
Block: 669480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735266 RingCT/type: yes/0
Extra: 01d0c1fe4aac0fb194624f08e0cf804f7651ea41311eb15d2fcf58b7588fdd04bc02110000000352542ceb000000000000000000

1 output(s) for total of 3.713084251000 dcy

stealth address amount amount idx
00: 6f43ee22b3485c42a3a4ab9ac3afca841a3cdd6e68df08a69c2a7889929faf2b 3.713084251000 1110801 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": 669490, "vin": [ { "gen": { "height": 669480 } } ], "vout": [ { "amount": 3713084251, "target": { "key": "6f43ee22b3485c42a3a4ab9ac3afca841a3cdd6e68df08a69c2a7889929faf2b" } } ], "extra": [ 1, 208, 193, 254, 74, 172, 15, 177, 148, 98, 79, 8, 224, 207, 128, 79, 118, 81, 234, 65, 49, 30, 177, 93, 47, 207, 88, 183, 88, 143, 221, 4, 188, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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