Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc8a533e193c7e8c64fc32630351eaf99d425811f65b420a68c1efdb2d01591

Tx prefix hash: 132c860e4800ee88c0ba282bdf52d8de977724e6083c30678494f9aad51d5567
Tx public key: 29ae53ea618597b342a5ce4e022e0b40d49fab36f2e27cad4cc80d30fac4f8f2
Timestamp: 1745733951 Timestamp [UCT]: 2025-04-27 06:05:51 Age [y:d:h:m:s]: 00:014:10:37:22
Block: 1270386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10332 RingCT/type: yes/0
Extra: 0129ae53ea618597b342a5ce4e022e0b40d49fab36f2e27cad4cc80d30fac4f8f202110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 805b2a769170b355872c4adc5cfb38bfeb6e66a8dd121f6036b3e13a6955a7df 0.600000000000 1757629 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": 1270396, "vin": [ { "gen": { "height": 1270386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "805b2a769170b355872c4adc5cfb38bfeb6e66a8dd121f6036b3e13a6955a7df" } } ], "extra": [ 1, 41, 174, 83, 234, 97, 133, 151, 179, 66, 165, 206, 78, 2, 46, 11, 64, 212, 159, 171, 54, 242, 226, 124, 173, 76, 200, 13, 48, 250, 196, 248, 242, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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