Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8189647fcf961857ae44ea98fb497765735d8d571a288033af5dc2f847de3b66

Tx prefix hash: a6b030a287708d1df4f7f584b23db3816529480dcd80e95dbb51a7612070ba6f
Tx public key: 77f2e4ce377b17189358c7c2e798813901abcf317b6a5ffb148ea453c586c0e8
Timestamp: 1764257017 Timestamp [UCT]: 2025-11-27 15:23:37 Age [y:d:h:m:s]: 00:026:08:42:52
Block: 1421347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18853 RingCT/type: yes/0
Extra: 0177f2e4ce377b17189358c7c2e798813901abcf317b6a5ffb148ea453c586c0e8021100000003fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 319ec2197b68c3d9ab503eb98c8b26fb486ed092b2e628d03ae84961f1701d2b 0.600000000000 1909904 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": 1421357, "vin": [ { "gen": { "height": 1421347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "319ec2197b68c3d9ab503eb98c8b26fb486ed092b2e628d03ae84961f1701d2b" } } ], "extra": [ 1, 119, 242, 228, 206, 55, 123, 23, 24, 147, 88, 199, 194, 231, 152, 129, 57, 1, 171, 207, 49, 123, 106, 95, 251, 20, 142, 164, 83, 197, 134, 192, 232, 2, 17, 0, 0, 0, 3, 251, 143, 208, 137, 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