Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2823b78b8b6830ef61dd099349d1bbd9a4b249368e8eb214327972cc7aba55

Tx prefix hash: 4352329cb847c58c39354b9bcd6e3f4b83b80772049a17197cd42133f1d163a8
Tx public key: 1eab3eafdf6836b2d3147275d40e42aed820a233a39bbc08a6f0170f04ee8a7f
Timestamp: 1750205193 Timestamp [UCT]: 2025-06-18 00:06:33 Age [y:d:h:m:s]: 00:149:23:59:09
Block: 1307274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105015 RingCT/type: yes/0
Extra: 011eab3eafdf6836b2d3147275d40e42aed820a233a39bbc08a6f0170f04ee8a7f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c8f0cb815cd0317966b8929a6c805d6d547f2d667e2860adc8ab8477cfed884 0.600000000000 1794885 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": 1307284, "vin": [ { "gen": { "height": 1307274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c8f0cb815cd0317966b8929a6c805d6d547f2d667e2860adc8ab8477cfed884" } } ], "extra": [ 1, 30, 171, 62, 175, 223, 104, 54, 178, 211, 20, 114, 117, 212, 14, 66, 174, 216, 32, 162, 51, 163, 155, 188, 8, 166, 240, 23, 15, 4, 238, 138, 127, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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