Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 316cbcd405ae9b32bc3cd137a19855bd3a6f686dc5d128df79c8adba8ca9094b

Tx prefix hash: 998f305f01a0e6fc61cbdf57e4ef81a327ce688e525e0689a4b19ced941659bb
Tx public key: 27f43dc7580ff62df4a83866c4ca48f101421d4f3052991c71c0ce3982b18c16
Timestamp: 1739797579 Timestamp [UCT]: 2025-02-17 13:06:19 Age [y:d:h:m:s]: 00:233:14:30:57
Block: 1221216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164688 RingCT/type: yes/0
Extra: 0127f43dc7580ff62df4a83866c4ca48f101421d4f3052991c71c0ce3982b18c160211000000181f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 641a65a64ee61b7f5f615349f55bbffee5a1579444fc03d62b3a071fd928fc34 0.600000000000 1708061 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": 1221226, "vin": [ { "gen": { "height": 1221216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "641a65a64ee61b7f5f615349f55bbffee5a1579444fc03d62b3a071fd928fc34" } } ], "extra": [ 1, 39, 244, 61, 199, 88, 15, 246, 45, 244, 168, 56, 102, 196, 202, 72, 241, 1, 66, 29, 79, 48, 82, 153, 28, 113, 192, 206, 57, 130, 177, 140, 22, 2, 17, 0, 0, 0, 24, 31, 10, 83, 235, 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