Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 421a654aba4530f659b52c9aea3ff0f12e177916ae73cb12710282156655bc42

Tx prefix hash: 2721a0532e401a31b487a75fbb871c08409fadee9c0b42fe69760a03e4e3582f
Tx public key: 7a5d435f9fb771be9a1507da426b2474c3f052730cff53ffa52e7902c741cf08
Timestamp: 1699306261 Timestamp [UCT]: 2023-11-06 21:31:01 Age [y:d:h:m:s]: 02:003:07:49:26
Block: 885999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522148 RingCT/type: yes/0
Extra: 017a5d435f9fb771be9a1507da426b2474c3f052730cff53ffa52e7902c741cf0802110000000633af99f4000000000000000000

1 output(s) for total of 0.711733686000 dcy

stealth address amount amount idx
00: e1b29c88d29e1cf75306004b1e7f8672aed20918f5e890761f64777c78b6c81c 0.711733686000 1341802 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": 886009, "vin": [ { "gen": { "height": 885999 } } ], "vout": [ { "amount": 711733686, "target": { "key": "e1b29c88d29e1cf75306004b1e7f8672aed20918f5e890761f64777c78b6c81c" } } ], "extra": [ 1, 122, 93, 67, 95, 159, 183, 113, 190, 154, 21, 7, 218, 66, 107, 36, 116, 195, 240, 82, 115, 12, 255, 83, 255, 165, 46, 121, 2, 199, 65, 207, 8, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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