Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 183bc9ef872d1f06ca6d6009d47f28f39299efffe67a183570c577f2cb3557f1

Tx prefix hash: ea0007029c2e3aa0ca6f4b0f5988c7bc94cdcf30070fd9886e7e751a68e2387a
Tx public key: ef0e919666b1459e70e0a4123de894d1dabd5618b0c20a04798612aa3d021444
Timestamp: 1731168219 Timestamp [UCT]: 2024-11-09 16:03:39 Age [y:d:h:m:s]: 00:014:22:05:17
Block: 1150063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10675 RingCT/type: yes/0
Extra: 01ef0e919666b1459e70e0a4123de894d1dabd5618b0c20a04798612aa3d021444021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b52ea2dcacb156de3c9c1e04b1cc9e174bf54e855b20ef7f12bf351b52192f71 0.600000000000 1635264 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": 1150073, "vin": [ { "gen": { "height": 1150063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b52ea2dcacb156de3c9c1e04b1cc9e174bf54e855b20ef7f12bf351b52192f71" } } ], "extra": [ 1, 239, 14, 145, 150, 102, 177, 69, 158, 112, 224, 164, 18, 61, 232, 148, 209, 218, 189, 86, 24, 176, 194, 10, 4, 121, 134, 18, 170, 61, 2, 20, 68, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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