Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10402440363487050402d771b2fc5da7183e0041f3d030f4330a73c6d02dedc6

Tx prefix hash: 5c801d7a526b7f280268b6a0f15a2e9358cdc23d11002b3bab83c48bd850e20e
Tx public key: f94741758c20b73cabb8891c69bcae0f67ff5be2507a731c392a5880c3fcffd4
Timestamp: 1730930316 Timestamp [UCT]: 2024-11-06 21:58:36 Age [y:d:h:m:s]: 00:000:09:41:24
Block: 1148092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284 RingCT/type: yes/0
Extra: 01f94741758c20b73cabb8891c69bcae0f67ff5be2507a731c392a5880c3fcffd402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a3df1af85891cc468dd2d878d7a1ba1e2b42ae4e7226e36d73dbf3c29c85d4 0.600000000000 1632855 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": 1148102, "vin": [ { "gen": { "height": 1148092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a3df1af85891cc468dd2d878d7a1ba1e2b42ae4e7226e36d73dbf3c29c85d4" } } ], "extra": [ 1, 249, 71, 65, 117, 140, 32, 183, 60, 171, 184, 137, 28, 105, 188, 174, 15, 103, 255, 91, 226, 80, 122, 115, 28, 57, 42, 88, 128, 195, 252, 255, 212, 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