Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c73964bf2d42c14691b7084454ec9de5dc71731cb2148473d63b36bce98137c

Tx prefix hash: a6263fbe5ff8304ed3ff3cd413d5ce2b110ac8130cb79c58b43f43d6726ca4a7
Tx public key: 0cdd0359af17a3e04611787b0905baedb0925acd1bd5f54f3ec46f20f483332d
Timestamp: 1682896311 Timestamp [UCT]: 2023-04-30 23:11:51 Age [y:d:h:m:s]: 01:345:07:41:49
Block: 750201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508051 RingCT/type: yes/0
Extra: 010cdd0359af17a3e04611787b0905baedb0925acd1bd5f54f3ec46f20f483332d021100000008b3164c24000000000000000000

1 output(s) for total of 2.005731830000 dcy

stealth address amount amount idx
00: 7e6fe115fc7d1aae2ba6afca4cdd7f91ac0eaff4dfc3fbae08eca475e258d3e4 2.005731830000 1198256 of 0

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": 750211, "vin": [ { "gen": { "height": 750201 } } ], "vout": [ { "amount": 2005731830, "target": { "key": "7e6fe115fc7d1aae2ba6afca4cdd7f91ac0eaff4dfc3fbae08eca475e258d3e4" } } ], "extra": [ 1, 12, 221, 3, 89, 175, 23, 163, 224, 70, 17, 120, 123, 9, 5, 186, 237, 176, 146, 90, 205, 27, 213, 245, 79, 62, 196, 111, 32, 244, 131, 51, 45, 2, 17, 0, 0, 0, 8, 179, 22, 76, 36, 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