Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b32c9696dcbaa80304b5f8b98533905dfc350c8fe4572259c73658194bdb35c1

Tx prefix hash: 47887506d7db267d6ea7df74a387da835fedf05579fca81bc42cc4fa424497ea
Tx public key: 8f4706e34266f24475124847c9db910a17baa31b6f732f4c4976628f6ef0a1bd
Timestamp: 1726839167 Timestamp [UCT]: 2024-09-20 13:32:47 Age [y:d:h:m:s]: 00:177:13:10:36
Block: 1114256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126717 RingCT/type: yes/0
Extra: 018f4706e34266f24475124847c9db910a17baa31b6f732f4c4976628f6ef0a1bd021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa8e37e4d533a51376f2d3e7d79beb8576f8935ac5567cdc01709e2ad6f2d7ae 0.600000000000 1594055 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": 1114266, "vin": [ { "gen": { "height": 1114256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa8e37e4d533a51376f2d3e7d79beb8576f8935ac5567cdc01709e2ad6f2d7ae" } } ], "extra": [ 1, 143, 71, 6, 227, 66, 102, 242, 68, 117, 18, 72, 71, 201, 219, 145, 10, 23, 186, 163, 27, 111, 115, 47, 76, 73, 118, 98, 143, 110, 240, 161, 189, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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