Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879c4efb40fb2432a317f07d7d5d34acda1a4962a6f53cfb118f88581a4ba88a

Tx prefix hash: c785dc2a0a747db9df1c7c436026a26c42348e4c5cac01a9754a4d2043975eaa
Tx public key: 39322f94eda4c26f97d96223c94d77bda801b215c24a4f18ae70ea4641abd9cf
Timestamp: 1648626969 Timestamp [UCT]: 2022-03-30 07:56:09 Age [y:d:h:m:s]: 02:350:04:42:00
Block: 469439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769693 RingCT/type: yes/0
Extra: 0139322f94eda4c26f97d96223c94d77bda801b215c24a4f18ae70ea4641abd9cf02110000000cc9067537000000000000000000

1 output(s) for total of 17.082599928000 dcy

stealth address amount amount idx
00: b52fff6a6a2f29467fe3d204cfb8eb98dbf2606830eb41bb07ec881d76f4e3e4 17.082599928000 888387 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": 469449, "vin": [ { "gen": { "height": 469439 } } ], "vout": [ { "amount": 17082599928, "target": { "key": "b52fff6a6a2f29467fe3d204cfb8eb98dbf2606830eb41bb07ec881d76f4e3e4" } } ], "extra": [ 1, 57, 50, 47, 148, 237, 164, 194, 111, 151, 217, 98, 35, 201, 77, 119, 189, 168, 1, 178, 21, 194, 74, 79, 24, 174, 112, 234, 70, 65, 171, 217, 207, 2, 17, 0, 0, 0, 12, 201, 6, 117, 55, 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