Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b832461217758cb25704756dbbdc23f0f3e1f9f6fddd866becbefcbb9c57815c

Tx prefix hash: 44a67bfe593c4a9b0811a6acc1109455a9dc880a053aab6eabbbd5268cfeb2d5
Tx public key: 56230fe4c7389cda17a782b12004e0479cb0e54815d2e96ce5f5d51a2308b43d
Timestamp: 1705372965 Timestamp [UCT]: 2024-01-16 02:42:45 Age [y:d:h:m:s]: 01:308:11:48:31
Block: 936265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479317 RingCT/type: yes/0
Extra: 0156230fe4c7389cda17a782b12004e0479cb0e54815d2e96ce5f5d51a2308b43d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be1b238b72df4532dc164dffcc7cf32aac9eacb34e224cab7e08cb12c665ed5c 0.600000000000 1394289 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": 936275, "vin": [ { "gen": { "height": 936265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be1b238b72df4532dc164dffcc7cf32aac9eacb34e224cab7e08cb12c665ed5c" } } ], "extra": [ 1, 86, 35, 15, 228, 199, 56, 156, 218, 23, 167, 130, 177, 32, 4, 224, 71, 156, 176, 229, 72, 21, 210, 233, 108, 229, 245, 213, 26, 35, 8, 180, 61, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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