Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f14da6540941f3b259743b6798b815ee7ab81e2507d3f9e5c720d842c5b2da5

Tx prefix hash: 2d6e1a82d27e098a30f51f62701554c86fa8e49700bf37c1118a81851cbad97c
Tx public key: f11c5fd8dd741ebb82a681b09d05a87a895dab39c00b2da9079c46a305d991d5
Timestamp: 1735371651 Timestamp [UCT]: 2024-12-28 07:40:51 Age [y:d:h:m:s]: 00:083:11:26:53
Block: 1184870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59443 RingCT/type: yes/0
Extra: 01f11c5fd8dd741ebb82a681b09d05a87a895dab39c00b2da9079c46a305d991d50211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca9698ce3a26deda8bde53dbfe3e3d140867e57c2e9a15722a86fd55fd54406c 0.600000000000 1671329 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": 1184880, "vin": [ { "gen": { "height": 1184870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca9698ce3a26deda8bde53dbfe3e3d140867e57c2e9a15722a86fd55fd54406c" } } ], "extra": [ 1, 241, 28, 95, 216, 221, 116, 30, 187, 130, 166, 129, 176, 157, 5, 168, 122, 137, 93, 171, 57, 192, 11, 45, 169, 7, 156, 70, 163, 5, 217, 145, 213, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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