Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff616d21ffa9e16288b90ce10c34acd43a8413d6bb47350476dc18aea28d81f6

Tx prefix hash: bf3950a7e08ceac1eb74085a5d4ad6f516fca99042f92693e313e7948143770e
Tx public key: 9e809292ce2f279209117f4b8d74e1065fe4883e2e57ddb12330480a88ca218a
Timestamp: 1717401928 Timestamp [UCT]: 2024-06-03 08:05:28 Age [y:d:h:m:s]: 00:344:07:49:17
Block: 1036027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246094 RingCT/type: yes/0
Extra: 019e809292ce2f279209117f4b8d74e1065fe4883e2e57ddb12330480a88ca218a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db1dc9b74697b0cf574d6ffbefc0d44fbac0a53125b0f5cecf3a2fae159b5f5 0.600000000000 1504552 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": 1036037, "vin": [ { "gen": { "height": 1036027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db1dc9b74697b0cf574d6ffbefc0d44fbac0a53125b0f5cecf3a2fae159b5f5" } } ], "extra": [ 1, 158, 128, 146, 146, 206, 47, 39, 146, 9, 17, 127, 75, 141, 116, 225, 6, 95, 228, 136, 62, 46, 87, 221, 177, 35, 48, 72, 10, 136, 202, 33, 138, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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