Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dcc8f3ded6de5a12980075162856caf3236c84064509716574c76450f219b96

Tx prefix hash: 6f55a50a88b6d86bac2f7ba9372282963322f2bee88b604b9fb8b2e5748e7e1f
Tx public key: 29b08f37f8b83b342493ff1321235e81c320568f8fba55d4f9b314ff979549d7
Timestamp: 1733870788 Timestamp [UCT]: 2024-12-10 22:46:28 Age [y:d:h:m:s]: 00:157:01:34:48
Block: 1172456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112066 RingCT/type: yes/0
Extra: 0129b08f37f8b83b342493ff1321235e81c320568f8fba55d4f9b314ff979549d7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc0f93fb503a90f9edd22f671fe8406fc7a3059f114591d194c1b2d2cb9a2a7e 0.600000000000 1658347 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": 1172466, "vin": [ { "gen": { "height": 1172456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc0f93fb503a90f9edd22f671fe8406fc7a3059f114591d194c1b2d2cb9a2a7e" } } ], "extra": [ 1, 41, 176, 143, 55, 248, 184, 59, 52, 36, 147, 255, 19, 33, 35, 94, 129, 195, 32, 86, 143, 143, 186, 85, 212, 249, 179, 20, 255, 151, 149, 73, 215, 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