Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e50fe307d0dd339d20eb22739c756b478fae3aef5a09d73416d7f68babf96b6

Tx prefix hash: 174bf2cf7cb3cf95c3b04ff957c03e89bf17ebcd89bc9a315fe9d721d7d4f29d
Tx public key: 76bc6f94d1b431971a20009b91c7ee0fd2b1defdf4e7711a64215f111d5311e4
Timestamp: 1762829244 Timestamp [UCT]: 2025-11-11 02:47:24 Age [y:d:h:m:s]: 00:054:20:37:30
Block: 1409508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39298 RingCT/type: yes/0
Extra: 0176bc6f94d1b431971a20009b91c7ee0fd2b1defdf4e7711a64215f111d5311e4021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64bf0fc2be2d8c0180942b0429782b035877d2ddebde281bf42186653ff9f054 0.600000000000 1897955 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": 1409518, "vin": [ { "gen": { "height": 1409508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64bf0fc2be2d8c0180942b0429782b035877d2ddebde281bf42186653ff9f054" } } ], "extra": [ 1, 118, 188, 111, 148, 209, 180, 49, 151, 26, 32, 0, 155, 145, 199, 238, 15, 210, 177, 222, 253, 244, 231, 113, 26, 100, 33, 95, 17, 29, 83, 17, 228, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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