Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de820849a15a0a560c55a1c86868732bc3707d6c873409e98ddba01ea7634409

Tx prefix hash: fe3f4725337dab0d48502907e21f491d3846ae2b25a74ec58e267c92ea3447ab
Tx public key: 99d421d00cb9c69be430eb73bc7b24ae828e3f35fc9b085dad828d6c1b1bf3bc
Timestamp: 1720387294 Timestamp [UCT]: 2024-07-07 21:21:34 Age [y:d:h:m:s]: 00:259:12:06:49
Block: 1060768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185395 RingCT/type: yes/0
Extra: 0199d421d00cb9c69be430eb73bc7b24ae828e3f35fc9b085dad828d6c1b1bf3bc021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f154d2af1d03322e651c19241ed9d4a568310432f7e70e9d84aa34ab2b395628 0.600000000000 1531253 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": 1060778, "vin": [ { "gen": { "height": 1060768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f154d2af1d03322e651c19241ed9d4a568310432f7e70e9d84aa34ab2b395628" } } ], "extra": [ 1, 153, 212, 33, 208, 12, 185, 198, 155, 228, 48, 235, 115, 188, 123, 36, 174, 130, 142, 63, 53, 252, 155, 8, 93, 173, 130, 141, 108, 27, 27, 243, 188, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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