Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5450ef51bc0582520b592e2dad6fc6ffea54f3c5d938d9a5377834c1fb3f5c63

Tx prefix hash: acbc5cbddbf81ca70f98efc4db2df4d0b2c4df0a373fae67fb860715f1b242d7
Tx public key: 8315ca1bf4fa513742ed1e78c6d49b3e85f90f6d95304d361cbfe52c811ee43f
Timestamp: 1634946053 Timestamp [UCT]: 2021-10-22 23:40:53 Age [y:d:h:m:s]: 03:203:21:24:04
Block: 358444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 923838 RingCT/type: yes/0
Extra: 018315ca1bf4fa513742ed1e78c6d49b3e85f90f6d95304d361cbfe52c811ee43f02110000000106faf294000000000000000000

1 output(s) for total of 39.840670798000 dcy

stealth address amount amount idx
00: e13f0d968d4e0afa755c370b261c3c8c1312cd4d2645e4a353411bd226e93029 39.840670798000 730365 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": 358454, "vin": [ { "gen": { "height": 358444 } } ], "vout": [ { "amount": 39840670798, "target": { "key": "e13f0d968d4e0afa755c370b261c3c8c1312cd4d2645e4a353411bd226e93029" } } ], "extra": [ 1, 131, 21, 202, 27, 244, 250, 81, 55, 66, 237, 30, 120, 198, 212, 155, 62, 133, 249, 15, 109, 149, 48, 77, 54, 28, 191, 229, 44, 129, 30, 228, 63, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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